The EDB Postgres Advanced Server must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75 percent of maximum audit record storage capacity.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-259279	EPAS-00-008000	SV-259279r938890_rule		Medium

Description
Organizations are required to use a central log management system, so under normal conditions, the audit space allocated to the DBMS on its own server will not cause an issue. However, space will still be required on the DBMS server for audit records in transit, and, under abnormal conditions, this could fill up. Since a requirement exists to halt processing upon audit failure, a service outage would result. If support personnel are not notified immediately upon storage volume utilization reaching 75 percent, they are unable to plan for storage capacity expansion. The appropriate support staff include, at a minimum, the ISSO and the DBA/SA.

Description

Organizations are required to use a central log management system, so under normal conditions, the audit space allocated to the DBMS on its own server will not cause an issue. However, space will still be required on the DBMS server for audit records in transit, and, under abnormal conditions, this could fill up. Since a requirement exists to halt processing upon audit failure, a service outage would result. If support personnel are not notified immediately upon storage volume utilization reaching 75 percent, they are unable to plan for storage capacity expansion. The appropriate support staff include, at a minimum, the ISSO and the DBA/SA.

STIG	Date
EnterpriseDB Postgres Advanced Server (EPAS) Security Technical Implementation Guide	2023-11-20

Details

Check Text ( C-63018r938888_chk )
If Postgres Enterprise Manager (PEM) or another similar monitoring capability is not installed and configured to probe storage volume utilization of the PGDATA directory and notify appropriate support staff upon storage volume utilization reaching 75 percent, this is a finding. The default path for the PostgreSQL data directory (PGDATA) is /var/lib/edb/as/data, but this will vary according to local circumstances.

Check Text ( C-63018r938888_chk )

If Postgres Enterprise Manager (PEM) or another similar monitoring capability is not installed and configured to probe storage volume utilization of the PGDATA directory and notify appropriate support staff upon storage volume utilization reaching 75 percent, this is a finding.

The default path for the PostgreSQL data directory (PGDATA) is /var/lib/edb/as/data, but this will vary according to local circumstances.

Fix Text (F-62927r938889_fix)
Install PEM and configure a probe to monitor and notify appropriate support staff upon storage volume utilization reaching 75 percent. Instructions to create a custom probe can be found at: https://www.enterprisedb.com/docs/pem/latest/monitoring_performance/probes/#creating-a-custom-probe Example steps for creating a probe are below, using the thin client (browser) PEM interface. Refer also to the Supplemental Procedures document supplied with this STIG. Open the PEM web console in a browser. - Log in. - Click on the agent for the machine to be monitored. - Select "Management \| Probe Configuration". - Select "Disk Space" and set the check interval as warranted. - Select "Management \| Alerting". - Name the definition "Audit Log Full". - Select Template "Disk Consumption Percentage". - Set Frequency, Comparison Operator, and Thresholds (1 minute, >, 95/96/97 for example). - Enter the Mount Point for where the audit log is. - Click Notification tab. - Click Email all alerts. - Click "Execute Script" on Monitored Server. - Enter script to shut down postgres, generally "systemctl stop edb-as-". - Click Add/Change to save, click OK to exit dialog box.

Fix Text (F-62927r938889_fix)

Install PEM and configure a probe to monitor and notify appropriate support staff upon storage volume utilization reaching 75 percent.

Instructions to create a custom probe can be found at: https://www.enterprisedb.com/docs/pem/latest/monitoring_performance/probes/#creating-a-custom-probe

Example steps for creating a probe are below, using the thin client (browser) PEM interface. Refer also to the Supplemental Procedures document supplied with this STIG.

Open the PEM web console in a browser.

- Log in.
- Click on the agent for the machine to be monitored.
- Select "Management | Probe Configuration".
- Select "Disk Space" and set the check interval as warranted.
- Select "Management | Alerting".
- Name the definition "Audit Log Full".
- Select Template "Disk Consumption Percentage".
- Set Frequency, Comparison Operator, and Thresholds (1 minute, >, 95/96/97 for example).
- Enter the Mount Point for where the audit log is.
- Click Notification tab.
- Click Email all alerts.
- Click "Execute Script" on Monitored Server.
- Enter script to shut down postgres, generally "systemctl stop edb-as-".
- Click Add/Change to save, click OK to exit dialog box.